-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Fix nullability issues in SslConfiguration
#3953
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
As discovered in issue #3947, an NPE can be thrown when an `SslConfiguration` returns `null` for its keystore, truststore, or `SSLContext`, in particular, in `SslSocketManager`.
src/changelog/.2.x.x/3947_fix_SslSocketManager_null_keystore.xml
Outdated
Show resolved
Hide resolved
Co-authored-by: Volkan Yazıcı <[email protected]>
Would you prefer this in a unit test fashion or as a functional test? I can see the value in either. The unit tests would be useful around ensuring things work with null values, but a functional test could check that you can use a trust store without a key store for syslog appenders. |
I'd appreciate a unit test reproducing the failure reported in #3947 – it doesn't necessarily need to be exactly the same, but should dial effectively same eventual knobs to trigger it. To aid with the implementation, feel free to mock stuff that is unrelated for the test subject. You can read this as, "Please no Docker ITs, etc. Just simple JUnit tests I can run using |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
@vy I found the right spot to test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirmed that test fails on 2.x with the error reported in #3947.
As discovered in issue #3947, an NPE can be thrown when an
SslConfigurationreturnsnullfor its keystore, truststore, orSSLContext, in particular, inSslSocketManager. Other fixes are noted by IntelliJ's nullability analysis on some files I checked that useSslConfigurationinstances.This fixes #3947.